Skip to main content

This is a new service – your feedback will help us to improve it.

Birmingham City Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

THE BIRMINGHAM (HOLLY GARDENS, BIRMINGHAM GREAT PARK, RUBERY) TPO 1999

reference
800
name
THE BIRMINGHAM (HOLLY GARDENS, BIRMINGHAM GREAT PARK, RUBERY) TPO 1999
tree-preservation-order

undefined

TPO 800
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-2.000178 52.404110,-2.000188 52.404116,-2.000329 52.404080,-2.000730 52.403944,-2.001201 52.403802,-2.001441 52.403723,-2.001872 52.403556,-2.002207 52.403390,-2.002272 52.403366,-2.002458 52.403263,-2.002471 52.403272,-2.002614 52.403179,-2.002681 52.403110,-2.002703 52.403057,-2.002704 52.403025,-2.002683 52.403024,-2.002670 52.402976,-2.002655 52.402952,-2.002565 52.402884,-2.002538 52.402853,-2.002478 52.402750,-2.002442 52.402668,-2.002364 52.402537,-2.002026 52.402095,-2.001966 52.401996,-2.001923 52.401902,-2.001890 52.401870,-2.001917 52.401847,-2.001825 52.401725,-2.001830 52.401715,-2.001820 52.401710,-2.001778 52.401604,-2.001731 52.401564,-2.001595 52.401623,-2.001570 52.401644,-2.000724 52.402124,-1.998984 52.403343,-1.999186 52.403455,-2.000178 52.404110)))
point
POINT (-2.000977 52.402972)
notes
The shaded area represents those properties which fall within the outline of a Tree Preservation Order. To precisely identify trees protected by the Order, you can request a copy of the tree preservation order at the following link.
organisation
entry-date
2025-11-30
start-date
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Birmingham City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL